In this example from practice, exit and acceptance criteria have high overlap. The test approach and acceptance criteria are tuned with the stakeholders (see section x.y). Two levels of acceptance can be distinguished:

1. Acceptance of system XYZ by all stakeholders. This involves releasing the products for production.
2. Individual acceptance by the client(s) of each test level of the test level executed.

For level 1 acceptance, the test must be executed according to the agreed test strategy and the following guidelines are respected for any defects found: The products of XYZ can be taken into production (are accepted) if:

• There are no category A defects.
• A patch or workaround is available for category B defects. The developer must also submit a planning reporting how and when the problem will be solved structurally.
• A document is available for category C defects, explaining how these non-critical defects are dealt with.

For level 2 acceptance, the test team (responsible for the relevant test level) will be discharged if the aims as defined globally in section y.z and further specified in detailed test plans, if any, are achieved. This is also a Go/No Go decision to start executing the following test level.